Started data analysis #91
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…the graph "empty" or "filled"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added an option of initializeing a filtered or stiched index empty or randomly filled. This corresponds to the first argument of the 3rd assignment. I also started extracting some information about the behaviour of this addition by analyzing the results for the filtered and unfiltered queries recall according to the two versions of the index, "empty" and "filled". The results were pretty good as the average unfiltered recall has been increased from 12% up tp 50%. The analysis has been done using Python and the code with its result plots can be found in
/analysis/directory.